Predictive analytics for broadband over power line data

ABSTRACT

A system includes server that performs operations including obtaining, from sensors, measurements of physical parameters related to electrical power transmission and data transfer corresponding to a Broadband over Power Line (BPL) data links and a multi-use power interface configured to be electrically and communicatively coupled to a vehicle via the BPL data links. The operations also include receiving identification and location information, and a timestamp associated with a connector of the multi-use power interface, and then storing the measurements, the identification and location information, and the timestamp. The operations further include detecting a change of the connector, and identifying trends in parameters by comparing the measurements and the identification and location information to historical data. The operations also include predicting, based on correlating the identified trends to the detected change, a pending failure of a network or electrical component, and transmitting an alert indicating the pending failure to a stakeholder.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application to U.S. patentapplication Ser. No. 16/147,166 filed on Sep. 28, 2018, now U.S. Pat.No. 10,615,848 issued on Apr. 7, 2020, the disclosure of which is herebyincorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure is directed to systems and methods for monitoringand analyzing electrical and network components. More particularly, thepresent disclosure is directed to systems and methods for monitoring,sensing, managing, and analyzing data characterizing Broadband overPower Line (BPL) links, BPL modems, and other electrical and networkcomponents, where the data is collected at multi-use power interface.

BACKGROUND

The cabling and connectors used to connect vehicles (e.g., aircraft) toground power units are used in harsh environments such as airports wherethey are subject to weather, corrosive chemicals, temperature andhumidity fluctuations, moisture, and physical trauma caused by groundcarts, fuel trucks and catering vehicles sometimes running over thecabling. Over time, these harsh environments can result in faultyconditions in the cabling and connectors. Traditionally, extensivetrouble shooting is required to isolate faulty conditions in connectionsbetween a ground power unit and an aircraft.

Systems operating onboard a vehicle can generate as well as receivesignificant amounts of data. For example, in the case of an aircraft,advanced avionics, in-flight entertainment systems, catering systems,passenger systems, and other onboard systems generate and/or utilizesubstantial amounts of data. As just one particular example for anaircraft, significant data is generated in connection with onboardmonitoring systems, such as engine monitoring systems. Engine monitoringdata can include, for example, compression ratios, rotations per minute,temperature, vibration, and other engine operational data. In addition,inflight entertainment systems for aircraft also can involve significantdata, such as terabytes of data for a suite of movies.

BPL can be used to transmit data over electrical links (e.g., electricalcables connecting a vehicle to a ground power unit). BPL allowsrelatively high-speed digital data transmission over electric powerdistribution wiring by using higher frequencies, a wider frequencyrange, and different technologies from other forms of power-linecommunications to provide relatively high-rate data communications. BPLlinks can be used as part of power interfaces that electrically andcommunicatively couple ground power units to vehicles such as aircraft.However, conventional power interfaces provide little to no indicationof the health of electrical power or data communications links at thevehicle end of the power interfaces (e.g., a plug or connector mating apower interface cable to a vehicle such as an airplane).

There is therefore a need for an improved technology for quickly andaccurately monitoring health statuses of BPL links, BPL modems, andother electrical and network components at a multi-use power interfacein order to enhance reliability for both electrical power and high speeddigital communications in harsh operating environments.

SUMMARY

The present disclosure relates to a method, system, and apparatus formonitoring and analyzing data collected at a multi-use power interfacefor a vehicle (e.g., an airplane). In particular, the data includes BPLdata collected at a connector that is operable to connect the multi-usepower interface to a vehicle. The method, system, and apparatus quicklyand accurately monitor health statuses of BPL links, BPL modems, andother electrical and network components using standard networkmonitoring applications and processes at a multi-use power interface.

A system for analyzing data characterizing electrical and networkcomponents, the system includes a plurality of sensors configured tomeasure physical parameters related to electrical power transmission anddata transfer. The system also includes a server comprising a processor,and a memory storing instructions thereon, that when executed by theprocessor, cause the server to perform operations. The operationsinclude obtaining, from the plurality of sensors, measurements ofphysical parameters related to electrical power transmission and datatransfer corresponding to a plurality of Broadband over Power Line (BPL)data links and a multi-use power interface configured to be electricallyand communicatively coupled to a vehicle via the plurality of BPL datalinks. The operations also include receiving identification information,location information, and a timestamp associated with a connector of themulti-use power interface. The operations further include storing, inthe memory, the obtained measurements of the physical parameters, theidentification information, the location information, and the timestamp.The operations additionally include detecting a change of the connectorof the multi-use power interface. The operations also includeidentifying trends in parameters by comparing the stored measurements ofthe physical parameters, the stored identification information, and thestored location information to historical data. The operations furtherinclude predicting, based on correlating the identified trends to thedetected change, a pending failure of one or more of a network componentand an electrical component; and then transmitting an alert indicatingthe pending failure to a stakeholder associated with the one or more ofthe network component and the electrical component.

In another implementation, the plurality of sensors in the systeminclude one or more of a time domain reflectometer (TDR) and a frequencydomain reflectometer (FDR) configured to collect power quality data bycharacterizing electrical conductors in the plurality of BPL data links.

A computer implemented method for analyzing data characterizingelectrical and network components is also disclosed. The method includesobtaining, by a computing device, from a plurality of sensors,measurements of physical parameters related to electrical powertransmission and data transfer corresponding to a plurality of Broadbandover Power Line (BPL) data links and a multi-use power interfaceconfigured to be electrically and communicatively coupled to a vehiclevia the plurality of BPL data links. The method also includes receiving,at the computing device, identification information, locationinformation, and a timestamp associated with a connector of themulti-use power interface. The method further includes storing, in amemory of the computing device, the obtained measurements of thephysical parameters, the identification information, the locationinformation, and the timestamp. The method additionally includesdetecting, by the computing device, a change of the connector of themulti-use power interface. The method also includes identifying, by thecomputing device, trends in parameters by comparing the storedmeasurements of the physical parameters, the stored identificationinformation, and the stored location information to historical data. Themethod further includes predicting, by the computing device, based oncorrelating the identified trends to the detected change, a pendingfailure of one or more of a network component and an electricalcomponent; and then transmitting, from the computing device, an alertindicating the pending failure to a stakeholder associated with the oneor more of the network component and the electrical component.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the present teachings, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and constitute apart of this specification, illustrate implementations of the disclosureand together with the description, serve to explain the principles ofthe disclosure.

FIG. 1 is a diagram illustrating an example operating environmentincluding a multi-use power interface connected to a vehicle and aground power system, according to one or more implementations of thedisclosure.

FIG. 2 is a diagram illustrating an example multi-use power interfaceconnector that includes a user interface for displaying statuses ofelectrical and network characteristics, according to one or moreimplementations of the disclosure.

FIG. 3 is a diagram illustrating an example detachable adapter for amulti-use power interface connector that includes a user interface fordisplaying statuses of electrical and network characteristics, accordingto one or more implementations of the disclosure.

FIG. 4 is a diagram illustrating an example system for monitoringelectrical and network components, according to one or moreimplementations of the disclosure.

FIG. 5 is a diagram illustrating an example system architecture formonitoring electrical and network components, according to one or moreimplementations of the disclosure.

FIG. 6 is a diagram illustrating example system components for use inconnecting a multi-use power interface to a vehicle, according to one ormore implementations of the disclosure.

FIG. 7 illustrates a flowchart of a method for monitoring and analyzingBPL data collected at a connector of a multi-use power interface,according to one or more implementations of the disclosure.

FIG. 8 illustrates a flowchart of a method for performing predictiveanalytics with collected sensor data and BPL data, according to one ormore implementations of the disclosure.

FIG. 9 is a block diagram illustrating an example of a computing systemthat can be used in conjunction with one or more implementations of thedisclosure.

It should be noted that some details of the figures have been simplifiedand are drawn to facilitate understanding rather than to maintain strictstructural accuracy, detail, and scale.

DESCRIPTION

Reference will now be made in detail to the present teachings, examplesof which are illustrated in the accompanying drawings. In the drawings,like reference numerals have been used throughout to designate identicalelements. In the following description, reference is made to theaccompanying drawings that form a part thereof, and in which is shown byway of illustration specific examples of practicing the presentteachings. The following description is, therefore, merely exemplary.

The systems and methods disclosed herein monitor components of anelectrical power system and data network components by leveragingexisting electrical infrastructure (e.g., BPL modems and communicationlinks) to collect sensor data using standards based network monitoringapplications and processes.

The systems and methods use an enhanced connector (e.g., a smart stingerconnector or plug) of a multi-use power interface (e.g., a stingercable) that connects a vehicle (e.g., an airplane) to ground systems(e.g., ground power systems). The connector remains fully functional andcommunicative at all times and does not require a vehicle (e.g., anairplane) to be connected in order to determine the health of thestinger cable. The systems and methods also provide a robust assessmentof the functionality of the multi-use power interface, so that if thereis a communication issue (e.g., fault or malfunction) detected, theissue can be more readily isolated and corrected. Implementationsdisclosed herein support reliable ground operations (e.g., airportoperations), improve troubleshooting, and ensure that the responsibleorganization is identified and notified for corrective action. In someimplementations, big data analytics (e.g., predictive analytics) ensurethat the responsible organization is proactively notified when a failureof a monitored device is predicted. Such implementations enableproactive support for the devices being monitored. The systems andmethods enhance cyber security and reliability for both electrical powerand high speed digital communications in harsh operating environments,such as airports. The systems and methods disclosed herein monitor andanalyze the health and performance of an interface between a groundnetwork and airplane systems without requiring an airplane to beconnected and communicating with the ground network. In such scenarios,monitoring includes using local storage (e.g., in a storage device ormemory of the connector) to collect sensor data until reconnectionoccurs. Upon reconnection, some implementations then deliver of thelocally stored data along with time stamps on what occurred while nodata connection was available.

The systems and methods disclosed herein monitor and analyze BPL datacollected at a connector of a multi-use power interface in order todetect and predict health statuses of components of electrical andnetwork systems. More particularly, the systems and methods disclosedherein monitor both the electrical and network systems at an enhancedconnector of a multi-use power interface (e.g., an improved powerstinger plug). Some implementations use a Time Domain Reflectometer(TDR) or a Frequency Domain Reflectometer (FDR) to characterizeelectrical conductors in the connector of the multi-use power interface.As would be understood by one skilled in the relevant art, a TDR is anelectronic instrument that uses time-domain reflectometry, and a FDR isan electronic instrument that uses a frequency-domain sweep, tocharacterize and locate faults in electrical conductors, such as, forexample, cables (e.g., coaxial cables), and other electrical wiring. ATDR or FDR can also be used to locate discontinuities in an electricalconnector, printed circuit board, and other types of electrical paths.The systems and methods provide immediate functional statuses forcomponents of the monitored electrical and network systems, either in auser interface at the multi-use power interface, or at a user interfaceof a computing device that is communicatively coupled to the connectorof the multi-use power interface, but remote from the connector. In someimplementations, the connector of the multi-use power interface includesa display device, such as, for example, a touchscreen display device oran LCD screen, for presenting immediate functional statuses forcomponents of the electrical and network systems. In additional oralternative implementations, the connector of the multi-use powerinterface presents functional statuses for components of the monitoredelectrical and network systems by illuminating multicolor light emittingdiodes (LEDs) and strobe lights. For instance, such implementationscould use LEDs to indicate healthy data and electrical connections.

The systems and methods also flag conditions that could lead to failure.Additionally, the systems and methods collect sensor data, and storehistorical readings of such sensor data to enable big data analytics tobe performed. Such big data analytics can be used to predict, based onpatterns in the historical data and known past events (e.g., componentfailures and faults in electrical connections), conditions that couldlead to future events. In this way, data monitoring and analysisperformed by the systems and methods enable health prognostication forcomponents of the monitored electrical and network systems. The systemsand methods also characterize to cross-check the impedancecharacteristic of a gate power source and an electrical loadcharacteristic of a vehicle (e.g., an airplane).

The systems and methods monitor and analyze electrical and data healthinformation and present the analysis results (e.g., functional healthstatuses of data links) to a user such as, for example, a mechanic orground crewmember plugging a connector of a multi-use power interfaceinto a vehicle. In some implementations, the results are displayed in auser interface at a connector connecting a multi-use power interface toa vehicle (e.g., a stinger plug enhanced with a user interface). Theseimplementations provide functional health status information all the wayto a vehicle (e.g., an airplane). In additional or alternativeimplementations, the systems and methods also monitor and analyze powerquality information. According to some implementations, the analysis ofpower quality information is similar to power grid health monitoring.These electrical and data monitoring capabilities and health statusindications also enable data analytics and extend fault detectioncapabilities to fault prognostication for both the electrical power anddata connections of a multi-use power interface (e.g., a stinger cable).

FIG. 1 is a diagram showing an example operating environment 100 formonitoring and analyzing network and electrical components, inaccordance with at least one implementation of the present disclosure.As shown in FIG. 1, the operating environment 100 includes a multi-usepower interface 110 connected to an exemplary vehicle 120 and anexemplary ground power system 130.

In the example of FIG. 1, the multi-use power interface 110 is a cableconnected to the vehicle 120, and the vehicle 120 is an airplane.However, in other implementations, various different types of vehiclescan be employed for the vehicle 120 of the disclosed methods and systemsincluding, but not limited to airborne vehicles (e.g., airplanes,helicopters, drones, and other aircraft), space vehicles (e.g., spaceplanes and satellites), terrestrial vehicles (e.g., locomotives tanks,trucks, cars, motorcycles, electric bicycles, and other terrestrialmotor vehicles), and marine vehicles (e.g., ships, boats, and otherwatercraft).

As shown in FIG. 1, the vehicle 120 (e.g., the airplane) includes aconnector 140 mounted on the external surface of the body (e.g., afuselage) of the vehicle 120 so that the connector 140 of the vehicle120 is accessible to ground crew personnel. The connector 140 of thevehicle 120 comprises a plurality of sockets for mating with one end 160of the multi-use power interface 110.

The one end 160 of the multi-use power interface 110 includes aconnector 150 (see, e.g., connector 150 and connector housing 250 ofFIG. 2). The connector 150 comprises a plurality of pins (see, e.g.,pins 210 a, 210 b, 210 c, 220, 230 a and 230 b of FIG. 2). Withcontinued reference to FIG. 1, the other end 170 of the multi-use powerinterface 110 is connected to the ground power system 130. Although theground power system 130 is schematically illustrated as a ground powercart in the example operating environment 100 of FIG. 1, components ofthe ground power system 130 can be integrated into other physicalcomponents, such as, for instance, at an airplane gate, such as into ajetway or jet bridge system at an airport or airbase.

When the vehicle 120 is on the ground, ground crew personnel connect theconnector 150 of the multi-use power interface 110 to the connector 140of the vehicle 120 such that the connector 150 is both electrically andcommunicatively coupled to the connector 140 of the vehicle 120.

In certain implementations, the connector 150 is operable to beelectrically and communicatively coupled to the vehicle 120 via BPL datalinks. In addition to providing electrical and communicationsconnectivity between the vehicle 120 and the ground power system 130,the connector 150 is configured to monitor components of electrical andnetwork systems. In some implementations, a portion of this monitoringcan be performed whether the connector 150 is connected to the vehicle120 or not. For example, the connector 150 can report its own health andnetwork health before the connector 150 is connected to the vehicle 120.As shown in FIG. 1, the ground power system 130 can include amulti-communication network interface 104 for exchanging communicationsvia a ground-based network 102 using any communications protocol thatenables broadband communication. In one example, the ground-basednetwork 102 can be embodied as an Internet Protocol (IP) network.

Similarly, some monitoring can be performed whether the connector 150 isconnected to the ground power system 130 or not. For example, whendisconnected from one or both the vehicle 120 and the ground powersystem 130, the connector 150 can obtain data from sensors (not shown,but see handheld BPL modem 511 and endpoint BPL modem 514 in FIG. 5)that are configured to monitor and collect data characterizingfunctional health statuses of electrical conductors and data linkswithin the connector 150 itself. In some implementations, local storage(e.g., a memory or storage device within the connector 150) can be usedwhile the connector is disconnected from the ground power system 130 inorder to store pertinent data until a reconnection with the ground powersystem 130 occurs.

When the connector 150 is connected to the vehicle 120, the monitoredcomponents include components of electrical and network systems on thevehicle 120. For example, the connector 150 can be configured to beelectrically and communicatively coupled to the vehicle 120 via BPL datalinks. In such implementations, the connector 150 can receive powerquality data and load management data from sensors that are configuredto collect power quality data and load management data for transmissionover the BPL data links at the vehicle 120, and for the connector 150itself. When the connector 150 is connected to the ground power system130, the monitored components can include electrical and networkcomponents within the ground power system 130. In variousimplementations, the connector 150 transmits, via data links in themulti-use power interface 110, the received power quality data and loadmanagement data to a remote store or data repository for analysis. Insome implementations, this analysis can include using big data analyticstechniques to determine, based on sensor data received by the connector150, respective functional health statuses of monitored network andelectrical components. Such sensor data can include historical datareceived and stored by the connector or by another storage device overtime. The analysis can also include determining, based on the receivedsensor data, functional health statuses of alternating current (AC)power lines (e.g., stinger AC lines) when the connector 150 is notconnected to the aircraft vehicle 120 and when the connector 150 isconnected to the aircraft vehicle 120. In certain implementations, thisdata can be forwarded to a centralized network monitoring application.In additional or alternative implementations, the analysis can alsoinclude real-time monitoring and management of BPL modem operations andmodem links. The analysis can also include using data analytics todetermine stinger AC line health history. As will be described in moredetail below with reference to FIG. 2, the analysis results (e.g.,functional health statuses of network and electrical components) can bedisplayed in real-time at the connector 150 in a user interface (see,e.g., user interface 290 of FIG. 2) via LED status indicators installedat the connector 150 (e.g., stinger connector) so that personnel at theaircraft interface with the connector 150 can immediately ascertain thefunctional health statuses. In some implementations, the connector 150can include application software with a graphical user interface (GUI)to view real-time analysis of the functional health status of theconnector 150 (e.g., stinger health) and the functional health statusesof network components such as BPL modems (e.g., operational statuses ofBPL modems). According to alternative or additional implementations,such functional health statuses can also be printed out in a report andviewed or printed with an interactive GUI operable to accept user inputin order to provider the user with the ability to control the parametersthat the user wishes to print or view.

As will be described in more detail below with reference to FIG. 2, themulti-use power interface 110 can comprise both optical portions (e.g.,an optical fiber(s) or fiber optic cable) and power portions (e.g.,electrical conductive materials). For example, connectors 140 and 150can comprise optical portions (e.g., an optical fiber(s) or fiber opticcable) and power portions (e.g., electrical conductive materials).During operation, data is transferred back and forth between at leastone onboard system (not shown) on the vehicle 120 and the components inthe ground power system 130 via connectors 140 and 150 and the multi-usepower interface 110. In addition, power is supplied to at least oneonboard system (not shown) on the vehicle 120 from the ground powersystem 130 via connectors 140 and 150 and the multi-use power interface110.

In various implementations, at least one onboard system of the vehicle120 can include various different types of systems including, but notlimited to, an avionics system, an aircraft control domain system, anaircraft information system, a video surveillance system, an inflightentertainment system, and/or a mission system. In at least oneimplementation, the data comprises at least one of aircraft controldomain data (e.g., avionics data, flight management computer data),aircraft information systems data (e.g., weather data, aircraft statedata, ambient temperature data, winds data, runway location data, flightlevel for descent data), or inflight entertainment data (e.g., moviesdata, music data, and games data).

It should be noted that in other implementations, the vehicle 120 cancomprise more than the single connector 140 depicted in FIG. 1. Inaccordance with such implementations, separate multi-use powerinterfaces 110 at connectors 150 will be connected respectively to theconnectors 140 of the vehicle 120. According to these implementations,the multi-use power interfaces 110 at connectors 150 can be connected tomore than one ground power system 130. In such implementations,components of electrical and network systems will be monitored by themulti-use power interfaces 110 at connector 150 and the monitored datawill be transmitted to a central data store or data repository foranalysis. In scenarios where the connector 150 is not connected to aground power system 130, the monitored data is stored in a local datastore at the connector 150. For example, if the connector 150 istemporarily disconnected from the ground power system 130, datacollected from sensors is stored in a local memory or storage medium atthe connector 150 until reconnection with the ground power system 130occurs.

FIG. 2 is a diagram 200 showing an exemplary user interface 290 of aconnector 150 of the multi-use power interface 110 of FIG. 1, inaccordance with at least one implementation. As shown in diagram 200,the example multi-use power interface connector 150 includes a userinterface 290 for displaying statuses of electrical and networkcharacteristics. To produce, store, and display the results presented inthe user interface 290, the connector can include a processor (e.g., acentral processing unit (CPU)) and local data storage (not shown, butsee processor unit 904 and storage devices 916 of FIG. 9). For example,the connector 150 can include integrated, processor-basedcurrent/voltage/temperature/magnetic field strength sensors (e.g., amultimeter with thermometer and magnetometer), a BPL modem, and anembedded flat-screen display device, in addition to a locally hosteddata collection and analysis capability using local storage and anembedded CPU. In an exemplary implementation, the user interface 290 caninclude LEDs that are illuminated in colored patterns (e.g., blinkingred to indicate a fault or a passive circuit).

The connector 150 mounts (e.g., mates) to the connector 140 (as shown inFIG. 1) of the vehicle 120. The connector 150 comprises a housing 250having the user interface 290, an insulated base 260 and a sidewall 270extending around the base 260. According to some implementations, thehousing 250 can also include a machine readable optical bar code suchas, for example, a quick response code (QR code) or a radio-frequencyidentification (RFID) tag that can be read and used to uniquely identifythe multi-use power interface 110 and the connector 150.

In alternative or additional implementations shown in FIG. 2, theconnector 150 can include a wireless communications interface 292 forwirelessly communicating with a mobile device (not shown) runningapplication software for displaying an expanded version of the userinterface 290 on a display of the mobile device. For instance, themobile device can be embodied as a smartphone or a tablet device thatexecutes application software for rendering a version of the userinterface 290 on the display of the mobile device in either an ad-hocbasis or an infrastructure mode. The wireless communications interface292 can wirelessly communicate with the mobile device using one or morewireless communication protocols or technologies, including timedivision multiple access (TDMA), code division multiple access (CDMA),global system for mobile communications (GSM), Enhanced Data GSMEnvironment (EDGE), wideband code division multiple access (W-CDMA),Long Term Evolution (LTE), LTE-Advanced, Wi-Fi (such as IEEE 802.11),Bluetooth, Wi-MAX, near field communication (NFC) protocol, or any othersuitable wireless communications protocol. For example, the wirelesscommunications interface 292 can be implemented as a radio transceiverthat is integrated into the housing 250 and is operable to exchange datawirelessly with application software running on a smartphone or tabletdevice. In particular, the wireless communications interface 292 cancommunicate over several different types of wireless networks dependingon the range required for the communication. For example, a short-rangewireless transceiver (e.g., Bluetooth or NFC), a medium-range wirelesstransceiver (e.g., Wi-Fi), and/or a long-range wireless transceiver canbe used depending on the type of communication or the range of thecommunication.

As further shown in FIG. 2, the connector 150 can also include anexternal wired communications interface 294 that is integrated into thehousing 250 and that can be used to connect to a portable anddisconnect-able device that provides a user interface. In someimplementations, the wired communications interface 294 can be used tosend data to a portable device that displays an expanded version of theuser interface 290. The wired communications interface 294 can be usedto communicate with the portable device using one or more communicationprotocols or technologies, including an Internet Protocol (IP), a Serialconnection protocol, or any other suitable communication protocol. Insome implementations, the portable device can include a BPL modem thatcan communicate directly with or through the BPL modem that is includedwithin the connector 150. Also, for instance, the portable device caninclude electrical power sensors as an alternative to using internallyresident sensors within the connector 150. Further, for example, theportable device can be implemented as a dis-connectable AC power sensorthat includes a BPL modem and a display device for rendering an expandedversion of the user interface 290 shown in FIG. 2. In variousimplementations, the portable device can be connected to the connector150 through the wireless communications interface 292 or the wiredcommunications interface 294. That is, the portable device can have awired or wireless interconnection to the connector 150. In variousimplementations, the portable device can host and execute a stand-aloneapplication, it can access a custom extension of a centralizednetworking monitoring solution, or it can run a custom applicationfocused on metrics as required by that application. According to certainimplementations, the application can print or view current, historical,or predictive health statuses based on the results of data analytics(e.g., predictive analytics).

As depicted in FIG. 2, the user interface 290 includes status indicators290 a, 290 b, 290 c, 290 d, 290 e, and 290 f, which indicate respectivefunctional health statuses of electrical and network components. In someimplementations, the status indicators 290 a, 290 b, 290 c, 290 d, 290e, and 290 f are LEDs that can be illuminated in certain patterns (e.g.,colors, blinking, pulsing) to indicate functional health statusescorresponding to characteristics of electrical and data links. In theexample of FIG. 2, the status indicators 290 a, 290 b, 290 c, 290 d, 290e, and 290 f indicate the functional status of characteristics of data(e.g., data links), time, fiber (e.g., the current data transfer rate ofa 127 Megabit per second (Mbps) fiber data link), voltage, current, andphase A (e.g., voltage for a phase of a three-phase alternating current(AC) line).

In an example implementation, a processor of the connector 150 can causethe status indicator 290 a to be illuminated in green in response todetermining that BPL data links of the connector 150 are healthy (e.g.,operating within an expected data rate range). Also, for example, theprocessor of the connector 150 can cause the status indicator 290 a topulse yellow in response to determining that one or more BPL data linksof the connector 150 are operating below an expected data rate range(e.g., not healthy). Further, for example, the processor of theconnector 150 can cause the status indicator 290 a to blink red inresponse to determining that a majority (or all) of the BPL data linksof the connector 150 are operating below an expected data rate range.

As illustrated in FIG. 2, six pins 210 a, 210 b, 210 c, 220, 230 a, and230 b extend from the base 260 of the connector 150. Each pin 210 a, 210b, 210 c, 220, 230 a, and 230 b includes a straight tip power portion(an outer conductive ferrule with electrical conductivity material, suchas aluminum, copper or steel as metallic element) 280 a, 280 b, 280 c,280 d, 280 e, 280 f and an optical data link core portion (whichcomprises at least a single strand of single-mode or multi-mode typeoptical fiber or alternatively configured individually as Gigabit rangeEthernet ports with copper and fiber optic cable assembly) 240 a, 240 b,240 c, 240 d, 240 e, 240 f. The optical portion 240 a, 240 b, 240 c, 240d, 240 e, 240 f of each of the pins 210 a, 210 b, 210 c, 220, 230 a, 230b extends within and is coextensive (e.g., flush) with an end of thepower portion 280 a, 280 b, 280 c, 280 d, 280 e, 280 f of the pin 210 a,210 b, 210 c, 220, 230 a, 230 b. Alternatively, the connector 150includes only electrical conductivity material pins 210 a, 210 b, 210 c,220, 230 a, and 230 b, without an optical data link core portion.

In one or more implementations, the power portion 280 a, 280 b, 280 c ofpins 210 a, 210 b, 210 c delivers three-phase alternating current (AC)power (i.e., each of the three pins 210 a, 210 b, 210 c has a differentsinusoidal phase) to the vehicle 120. Pin 220 is a neutral pin andoperates as ground. Pins 230 a and 230 b are interlocking pins that areused to ensure that the pins 210 a, 210 b, 210 c, 220 of the connector150 are properly seated (e.g., mated) within sockets of the connector140 of the vehicle 120. As such, during operation, to prevent themulti-use power interface 110 from being energized with power before theconnector 150 is fully seated in connector 140 of the vehicle 120, theinterlocking pins 230 a and 230 b will not allow the ground power system130 to provide power to the multi-use power interface 110 and vehicle120 until the pins 210 a, 210 b, 210 c, 220, 230 a and 230 b are allfully seated within the sockets of connector 150. The interlocking pins230 a and 230 b are shorter in length to ensure that the longer pins 210a, 210 b, 210 c, 220 of the connector 150 are fully seated in thesockets of connector 140 of the vehicle 120. This protective featureprovided by the interlocking pins 230 a and 230 b provides arc flashmitigation (e.g., prevents arcing in the connector 150 to the aircraftvehicle 120) and provides safety to the ground crew (e.g., prevents theground crew from being shocked by handling a loose multi-use powerinterface 110 that is energized). According to some implementations,there can be a protective shield around the portable device.

According to an example implementation, the processor of the connector150 can cause the status indicator 290 d to be illuminated in green inresponse to determining that power portions (e.g., conductive portionscomprising electrical conductive materials) of the connector 150 areproviding voltages that are within an expected voltage range (e.g.,whether the provided voltage is 115+/−5 volts alternating current(Vac)). Further, for example, the processor of the connector 150 cancause the status indicator 290 d to pulse yellow in response todetermining that one or more power portions of the connector 150 are notproviding a voltage within the expected voltage range. Additionally, forinstance, the processor of the connector 150 can cause the statusindicator 290 d to blink red in response to determining that a majorityof the power portions of the connector 150 are not providing a voltagewithin the expected voltage range.

In another example implementation, the processor of the connector 150can cause the status indicator 290 e to be illuminated in green inresponse to determining that a current (e.g., amperage) provided by themulti-use power interface 110 is approximately an expected current(e.g., the amperage is in the normal range for a load profile indicatedin load management data). Further, for example, the processor of theconnector 150 can cause the status indicator 290 e to pulse yellow inresponse to determining the current (e.g., Amperage) provided by themulti-use power interface 110 is slightly below an expected current(e.g., the amperage is below the normal range). Additionally, forinstance, the processor of the connector 150 can cause the statusindicator 290 e to blink red in response to determining that the current(e.g., amperage) provided by the multi-use power interface 110 is wellbelow the expected current. According to some implementations, thebehavior of the portable device is configurable to enable customizationin how the portable device operates and whether it is implemented as astand-alone device or implemented as an extension of a centralizedsystem.

In yet another example implementation, the processor of the connector150 can cause the status indicator 290 f to be illuminated in green inresponse to determining that a phase separation from a power provided bythe multi-use power interface 110 is approximately an expected phaseseparation. Also, for instance, the processor of the connector 150 cancause the status indicator 290 f to blink red in response to determiningthat the phase separation from a power provided by the multi-use powerinterface 110 is not an expected phase separation.

When the vehicle 120 is on the ground, the connector 150 is electricallyconnected to at least one onboard system (not shown) on the vehicle 120,and more particularly, each pin 210 a, 210 b, 210 c, 220, 230 a and 230b is connected to at least one such onboard system to provide power viathe power portion 280 a, 280 b, 280 c, 280 d, 280 e, 280 f. In addition,each pin 210 a, 210 b, 210 c, 220, 230 a and 230 b is connected to atleast one such onboard system to enable communications (e.g., thetransfer of data) via the power portion (e.g., BPL links) 280 a, 280 b,280 c, 280 d, 280 e, 280 f and/or via the optical portion (e.g., datacommunications over the optical fiber(s) or fiber optic cable) 240 a,240 b, 240 c, 240 d, 240 e, 240 f. Regardless of whether the connector150 is electrically connected to the vehicle 120 or not, the userinterface 290 of the connector 150 is able to display functional healthstatuses of network and electrical components. For example, when theconnector 150 is disconnected from the vehicle 120, the user interface290 can still display functional health statuses for electrical andnetwork components by powering the embedded components within connector150 with Direct Current (DC) remotely power via interlocking pins 230 aand 230 b that the multi-use power interface 110 is connected to via theground power system 130 of FIG. 1. Once the connector 150 is connectedto the vehicle 120, the connector 150 can read impedance, receive loadmanagement data and obtain other diagnostic and sensor data from thevehicle 120. Such data can be used for predictive maintenance andtroubleshooting of network and electrical components on the vehicle 120.

The particular configurations for the connector 150 and the userinterface 290 can vary widely depending on the particular vehicle 120and onboard systems involved. The connector 150 and user interface 290shown in FIG. 2 is just one example connector and user interface. Forexample, the size, number, and arrangement of the status indicators 290a, 290 b, 290 c, 290 d, 290 e, and 290 f can vary according to thenumber and type of characteristics and components being monitored.Additionally, the user interface 290 can be embodied as a touchscreendisplay device or liquid-crystal display (LCD) or other suitableflat-panel display device incorporated into the housing 250. Forexample, an embedded touchscreen display device integrated into thehousing 250 of the connector can be used to present the user interface290 and to accept input from a user of the connector 150. Also, forexample, the size and number of pins 210 a, 210 b, 210 c, 220, 230 a and230 b can vary. The particular arrangement of pins 210 a, 210 b, 210 c,220, 230 a and 230 b can also vary. In addition, the materials for theconnector 150 selected can depend on the particular environment in whichthe vehicle 120 operates.

FIG. 3 is a diagram 300 illustrating an example detachable adapter 350for the multi-use power interface 110 of FIGS. 1 and 2, according to oneor more implementations of the disclosure. For brevity, only thedifferences occurring within the Figures, as compared to previous orsubsequent ones of the figures, are described below.

In accordance with certain implementations, all of the capabilities ofthe connector 150 described above with reference to FIGS. 1 and 2 arebuilt into the detachable adapter 350. For instance, as shown in FIG. 3,the detachable adapter 350 includes the wireless communicationsinterface 292, the wired communications interface 294, and the userinterface 290 for displaying statuses of electrical and networkcharacteristics. In particular, the user interface 290 and statusindicators 290 a, 290 b, 290 c, 290 d, 290 e, and 290 f configured toindicate respective functional health statuses of electrical and networkcomponents are integrated into a housing of the detachable adapter 350.

As illustrated in FIG. 3, six pins 210 a, 210 b, 210 c, 220, 230 a, and230 b extend from a base of the detachable adapter 350. As describedabove with reference to FIG. 2, each pin 210 a, 210 b, 210 c, 220, 230a, and 230 b includes a straight tip power portion (an outer conductiveferrule with electrical conductivity material, such as aluminum, copperor steel as metallic element) and an optical data link core portion(which comprises at least a single strand of single-mode or multi-modetype optical fiber or alternatively configured individually as Gigabitrange Ethernet ports with copper and fiber optic cable assembly). Theoptical portion of each of the pins 210 a, 210 b, 210 c, 220, 230 a, 230b extends within and is coextensive (e.g., flush) with an end of thepower portion of the pin 210 a, 210 b, 210 c, 220, 230 a, and 230 b.Alternatively, the detachable adapter 350 includes only electricalconductivity material pins 210 a, 210 b, 210 c, 220, 230 a, and 230 b,without a coextensive optical portion.

The pins 210 a, 210 b, 210 c, 220, 230 a, and 230 b extending from thebase of the detachable adapter 350 are adapted to be seated (e.g.,mated) within corresponding sockets or receptacles (not shown) withinconnector 140 of a vehicle (not shown, but see vehicle 120 in FIG. 1),which in turn includes pins 388 a-f to electrically and communicativelycouple the multi-use power interface 110 to the vehicle via thedetachable adapter 350. Similarly, respective ones of pins 380 a-f of astandard connector 355 (e.g., a standard stinger connector) are adaptedto be seated within respective ones of sockets 384 a-f at an end of thedetachable adapter 350. In some implementations, the standard connector355 does not include fiber optic capabilities or optical portions. Asshown in FIG. 3, the standard connector 355 is attached to one end 160of the multi-use power interface 110, and is connected via pins 380 a-fto the detachable adapter 350, which in turn is attached to theconnector 140 of the vehicle via pins 210 a, 210 b, 210 c, 220, 230 a,and 230 b. That is, the detachable adapter 350 can be used toelectrically and communicatively couple the one end 160 of the multi-usepower interface 110 to a vehicle in scenarios where the one end 160 hasthe standard connector 355. In this way, the detachable adapter 350shown in FIG. 3 can be used to provide the monitoring, analyzing, andreporting functionality of the connector 150 described above withreference to FIGS. 1 and 2 to a standard connector 355 that lacks suchcapabilities and does not include the user interface 290.

FIG. 4 is a diagram of an exemplary system 400 for use in monitoringelectrical and network components, such as, for example, components ofan aircraft network. In the example of FIG. 4, the system 400 works witha vehicle 120 (e.g., an airplane) on the ground at an airport, factory,maintenance facility, etc. As used herein the term “airport” refers toany location in which aircraft, such as fixed-wing airplanes,helicopters, blimps, or other aircraft take off and land. The system 400includes a power system or ground power system 130 (e.g., a ground powerunit) that supplies power to aircraft vehicle 120. In the exemplaryimplementation, the ground power system 130 is a ground-based power cartthat is mobile and that selectively supplies power to an aircraftvehicle parked on the ground at locations at, or adjacent to, theairport. In one implementation, ground power system 130 can be aconventional power delivery system used at airports. The ground powersystem 130 is coupled to the vehicle 120 when the vehicle 120 is parkedor docked (e.g., when an aircraft vehicle is parked at an airport). Inthe example of FIG. 4, the multi-use power interface 110 (e.g., a powerstinger cable) couples vehicle 120 to ground power system 130 via aconnector 150 (e.g., a stinger connector at the vehicle 120) and aground power interface connection 450 (e.g., another stinger connectorat the ground power system 130). In certain implementations, the groundpower interface connection 450 is operable to electrically andcommunicatively couple the multi-use power interface 110 to the vehicle120 via the ground power system 130 (e.g., ground power unit). In oneimplementation, ground power system 130 provides 400 hertz (Hz) power tothe vehicle 120 (e.g., aircraft) via the multi-use power interface 110.For example, the ground power interface connection 450 can be configuredto provide alternating current (AC) power to an airplane vehicle 120while engines of the airplane vehicle are off. However in alternativeimplementations, any suitable power for a particular type of vehicle 120can be provided via the multi-use power interface 110. In certainimplementations, the vehicle 120 includes an on-board BPL modem 411,that enables communication via multi-use power interface 110. Moreparticularly, in the example implementation of FIG. 4, the on-board BPLmodem 411 is coupled to connector 150 through coupler 410 (e.g., aninductive or capacitive coupler). The on-board BPL modem 411 is capableof communicating with an off-board BPL modem 414, included in groundpower system 130. The on-board BPL modem 411 can function as a repeaterby simultaneously communicating with off-board BPL modem 414, and otheron-board BPL modems 411 that may be in the vehicle 120. In the exampleof FIG. 4, while the vehicle 120 is parked, the on-board BPL modem 411is communicatively coupled to on-board networks 418 such as, but notlimited to, in-flight entertainment systems, avionics systems, flightcontrol systems, electronic flight bag(s), and cabin systems.

In the exemplary implementation shown in FIG. 4, ground power system 130includes off-board BPL modem 414 coupled to a coupler 416 (e.g., aninductive or capacitive coupler). Coupler 416 inductively orcapacitively couples off-board BPL modem 414 to the multi-use powerinterface 110. The coupler 416 also transfers communications signalsonto the multi-use power interface 110. The ground power system 130 alsoincludes a computing device 422 that can communicate directly with thevehicle 120 to transfer data to on-board networks 418. In the exemplaryimplementation, the off-board BPL modem 414 is also coupled to amulti-communication network interface 104 that is communicativelycoupled to the ground-based network 102. For example, in oneimplementation, the multi-communication network interface 104 is aground side interface that transmits data to/from the ground-basednetwork 102. The multi-communication network interface 104 can bewirelessly coupled to the ground-based network 102 through a wirelesstransceiver or physically coupled to the ground-based network 102through a wired connection. It should be noted that themulti-communication network interface 104 can communicate with theground-based network 102 using any protocol that enables broadbandcommunication. In one example, the ground-based network 102 can beembodied as an Internet Protocol (IP) network.

In the exemplary implementation shown in FIG. 4, the vehicle 120receives electrical power from ground power system 130 via the multi-usepower interface 110 and sends/receives data communications to/from theground-based network 102 via the multi-use power interface 110. Incertain implementations, the vehicle 120 communicates via the on-boardBPL modem 411 using the TCP/IP communications protocol within thenetwork, however any other suitable data communications protocol can beused. In some implementations, encryption is employed to further securecommunications between the vehicle 120 and ground-based network 102and/or computing device 422. For example, according to some suchimplementations, the data communications is encrypted using a protocolsuch as Secure Sockets Layer (SSL), Secure Shell (SSH), HypertextTransfer Protocol Secure (HTTPS), or another cryptographiccommunications protocol. Received power is distributed to a power bus428.

In alternative or additional implementations shown in FIG. 4, the groundpower system 130 can include a wireless interface 492 for wirelesslycommunicating (e.g., via encrypted communications) with a mobile device(not shown) running application software for displaying results ofmonitoring electrical and network components of the system 400. Forinstance, the mobile device can be embodied as a smartphone or a tabletdevice that executes application software for presenting a version ofthe user interface 290 shown in FIG. 2 on the mobile device's display.The wireless interface 492 can wirelessly communicate with the mobiledevice using one or more wireless communication protocols ortechnologies, including TDMA, CDMA, GSM, EDGE, W-CDMA, LTE,LTE-Advanced, Wi-Fi, Bluetooth, Wi-MAX, an NFC protocol, or any othersuitable wireless communications protocol. For example, the wirelessinterface 492 can be implemented as a radio transceiver that isintegrated into the ground power system 130 and is configured toexchange data wirelessly with application software running, on asmartphone or tablet device. More particularly, the wireless interface492 can communicate over several different types of wireless networksdepending on the range required for the communication. For example, ashort-range wireless transceiver (e.g., Bluetooth or NFC), amedium-range wireless transceiver (e.g., Wi-Fi), and/or a long rangewireless transceiver can be used depending on the type of communicationor the range of the communication. The application software can be astand-alone application running on the mobile or a mobile client (e.g.,a web-based client) of a centralized application hosted by theapplication server 424.

As additionally shown in FIG. 4, the ground power system 130 can furtherinclude an external wired interface 494 that can be used to connect to aportable and disconnect-able device that provides a user interface. Insome implementations, the wired interface 494 can be used to send datato a portable device that displays an expanded version of the userinterface 290 shown in FIG. 2. The wired interface 494 can be used tocommunicate with the portable device using one or more communicationprotocols or technologies, including an Internet Protocol (IP), a serialconnection protocol, or any other suitable communication protocol. In anexample, the portable device can be implemented as a dis-connectable ACpower sensor that includes a BPL modem and a display device forrendering an expanded version of the user interface 290 shown in FIG. 2.In various implementations, the portable device can be connected to theground power system 130 through the wireless interface 492 or the wiredinterface 494. That is, the portable device can have a wired or wirelessinterconnection to the ground power system 130.

Ground-based network 102 can be communicatively coupled to anapplication server 424 (e.g., a server or server farm hosting one ormore applications). The one or more applications can include astand-alone application for monitoring a custom status such as aparticular parameter or characteristic of a monitored electrical ornetwork component. Although only a single application server 424 isshown in FIG. 4, it is to be understood that the system 400 can includemultiple servers 424. The application server 424 can be operated by anairline or entity that owns, leases, or operates the vehicle 120.Alternatively, the application server 424 can be operated by athird-party, such as, for example, the airport, a vehicle manufacturer,and/or a vehicle service provider. For example, the application server424 can be coupled to ground-based network 102 via a local area network(LAN), a wide area network (WAN), and/or the Internet. The applicationserver 424 can transmit data to and receive data from the vehicle 120.For example, the application server 424 can provide software and/orfirmware updates to components of the vehicle 120, such as cabin systemssoftware, electronic flight bag (EFB), and avionics software. Theapplication server 424, or a stand-alone application running on theapplication server 424, can also provide content, such as music, movies,games, and/or internet data such as cached web content for in-flightentertainment systems on an aircraft vehicle 120. In one implementation,the system 400 is used to transfer data between the vehicle 120 andground-based network 102 during a quick-turn of the vehicle 120. As usedherein, the term “quick-turn” refers to a quick turn-around time (i.e.,less than about 40 minutes) of an aircraft vehicle at a gate betweenpassenger deplaning and boarding. During a quick-turn, content of theapplication server 424 or a stand-alone application running on theapplication server 424 can be refreshed and data stored on an on-boardserver 426 during a flight can be transmitted to the ground-basednetwork 102.

Although FIG. 4 illustrates the ground power system 130 as being coupledto the multi-use power interface 110 via the off-board BPL modem 414, itshould be appreciated that other configurations that enable theoff-board BPL modem 414 to function are possible. For example, theoff-board BPL modem 414 can communicate wirelessly with the on-boardmodem 411 when the vehicle 120 is directly coupled to the ground powersystem 130 via the multi-use power interface 110. As another example,the off-board BPL modem 414 can be configured to communicate wirelesslywith the vehicle 120 via the computing device 422 while at the sametime, communicate via the multi-use power interface 110 when power issupplied from the ground power system 130 to the vehicle 120.

In some implementations, the vehicle 120 includes a vehicle systemsinterface unit 432 that enables communication via the multi-use powerinterface 110. In the illustrated implementation, the vehicle systemsinterface unit 432 is coupled to the connector 150 along with theon-board BPL modem 411. In additional or alternative implementations,the vehicle systems interface unit 432 is coupled to a separateconnector (e.g., a separate stinger connector) from the on-board BPLmodem 411. Still other implementations can include the vehicle systemsinterface unit 432 without including the on-board BPL modem 411. Thevehicle systems interface unit 432 is communicatively coupled via one ormore BPL data links to a plurality of vehicle (e.g., aircraft) databuses 434. The data buses 434 can include any data buses carryinginformation on the vehicle 120, and can include the on-board networks418.

The vehicle systems interface unit 432 is connected to multiple databuses 434 to receive data from the data buses 434. The vehicle systemsinterface unit 432 asynchronously multiplexes the received data andconverts the received data to Ethernet packets for transmission over themulti-use power interface 110 to the ground power system 130. The groundpower system 130 includes a network communications interface 420. In theexemplary implementation shown in FIG. 4, the network communicationsinterface 420 includes a ground side vehicle systems interface unit 432.In additional or alternative implementations, the network communicationsinterface 420 includes a ground side aircraft systems interface unitthat is different than the vehicle systems interface unit 432. Thenetwork communications interface 420 receives the Ethernet packets sentby the vehicle systems interface unit 432 and decodes the data to itsoriginal format. Although the network communications interface 420 isillustrated as being within the ground power system 130, in otherimplementations it is separate from the ground power system 130.Moreover, the connection between the vehicle systems interface unit 432and the network communications interface 420 can be made with cabling,such as the multi-use power interface 110, that is used to provide powerand data communications to the vehicle 120 (e.g., BPL links functioningas a power cable capable of such delivery of power and datacommunications). Although data is described as being transmitted fromthe vehicle systems interface unit 432 to the network communicationsinterface 420, it should be understood that data can be transmitted inboth directions (i.e., data can be packetized and transmitted from thenetwork communications interface 420 to the vehicle systems interfaceunit 432).

The network communications interface 420 outputs the unpacked data to asecondary system 438. In the exemplary implementation, the secondarysystem 438 is a functional test unit (FTU). The FTU includes multipledevices for testing vehicle systems (e.g., aircraft systems), monitoringvehicle systems, providing sensor simulation, etc. In certainimplementations, the secondary system 438 can be a computing deviceconfigured to receive data from the network communications interface 420for testing, monitoring, analysis, fault detection, faultprognostication, simulation, etc. According to such implementations, thesecondary system 438 receives power quality data and load managementdata collected by sensors within the system 400. The sensors can beconfigured to perform preprocessing of at least one of power qualitydata or load management data. This preprocessing can include signalprocessing of voltages, currents, frequencies, or other parameters forelectrical signals detected and measured by the sensors. Thispreprocessing can include identifying harmonics, modulation, powerfactors, or other suitable types of parameters. The sensors can store atleast one of power quality data or load management data in raw form(e.g., raw sensor data) or preprocessed form. The sensors can send thisdata to one or both of the connector 150 and the application server 424in response to an event. In an implementation, an event can be, forexample, the expression of a timer, a data request from either theconnector 150 or the application server 424, or some other suitableevent.

In additional or alternative implementations, the power quality data andload management data collected by sensors is received at the connector150, where it is analyzed and used to determine and display (e.g., inthe user interface 290 of FIG. 2) a functional health status for themulti-use power interface 110, and functional health statuses of BPLdata links used to electrically and communicatively couple the multi-usepower interface 110 to the vehicle 120. Such power quality data and loadmanagement data can include, for example, characteristics of electricaland network components (e.g., one or more of electrical conductors inthe multi-use power interface 110, the on-board BPL modem 411, and theoff-board BPL modem 414, the power bus 428, and the data buses 434) inthe system 400. For example the power quality data can include one ormore of a voltage, a current, a frequency, a power, a reactive power, apower factor, voltage harmonics, current harmonics, a total harmonicdistortion, an amplitude voltage modulation, a frequency voltagemodulation, a current demand amplitude, a current demand frequencymodulation, a voltage ripple amplitude, a current ripple amplitude, acurrent ripple frequency, a voltage ripple frequency, a power interrupt,a magnetic field density (MFD), or another power quality parameterusable to determine a functional health status of a BPL data link. Also,for example, load management data can include one or more of a loadidentifier, current demand harmonics, a current demand amplitude, acurrent frequency modulation, a ripple current amplitude, a ripplecurrent frequency, a load impedance information, a load power factor,source impedance, impedance matching optimization, an MFD, phasormeasurements, impedance, or other load management parameters pertainingto an electrical load of the vehicle 120.

In still other implementations, the secondary system 438 can be atransceiver that is communicatively coupled (wired or wirelessly) to theground-based network 102 to transmit the data to a remote locationcoupled to the ground-based network 102.

FIG. 5 is a diagram illustrating an example system architecture 500 formonitoring electrical and network components, according to one or moreimplementations of the disclosure.

As shown, the system architecture 500 includes an application server424. Although only a single application server 424 is shown in FIG. 5,it is to be understood that the system architecture 500 can includemultiple application servers 424. One of the application servers 424 canfunction as a stand-alone device with a custom application. Theseapplication servers 424 can provide variety of applications to analyzeand display sensing, monitoring and management of electrical and networkcomponents. Such sensing can include receiving power quality data andload management data from a plurality of sensors that are configured tocollect the power quality data and the load management data for networkand electrical components, such as, but not limited to BPL data linksand the AC power lines included in a multi-use power interface 110 asshown in FIG. 5. The sensors can include one or more time domainreflectometers (TDRs) and frequency domain reflectometers (FDRs)configured to collect power quality data by characterizing electricalconductors in the plurality of BPL data links. In some implementations,the sensors can also include one or more optical time domainreflectometer (OTDRs) configured to collect load management data bycharacterizing the one or more fiber optic Gigabit data links in themulti-use power interface 110. In various implementations, the sensorscan also include one or more accelerometers, moisture sensors, ammeters,voltmeters, ohmmeters, MFD detectors, Internet of Things (IoT) sensors,a handheld BPL modem 511, and an endpoint BPL modem 514. The endpointBPL modem 514 in connector 150 can function as a repeater bysimultaneously communicating with off-board BPL modem 414, and otheron-board BPL modems 411 that may be in the vehicle 120.

A sensor can be configured to detect at least one of a current, avoltage, or a frequency as power quality data for an electricalcomponent of the system architecture 500. Current parameters areexamples of load management data. Example current parameters detectedand measured by a sensor can include single-phase alternating current(AC) currents, three-phase alternating current (AC) currents, or directcurrent (DC) currents. Other load management data that is used in thesystem architecture 500 along with current can include, for example, thesource configuration on the airplane vehicle 120 at the time the currentis recorded. The source configuration can be determined by using one ormore sensors to monitor source currents. The sensors can be configuredto perform preprocessing of power quality data and load management data.Examples of such preprocessing can include signal processing ofvoltages, currents, frequencies, or other parameters for electricalsignals detected and measured by the sensors. This preprocessing caninclude identifying harmonics, modulation, power factors, or othersuitable types of parameters. The sensors can store at least one ofpower quality data or load management data in raw form or preprocessedform (e.g., preprocessed sensor data). The sensors can send this data toone or more of the connector 150 and the application server 424 inresponse to events. In some implementations, event can include one ormore of an expression of a timer (e.g., a timer for a periodic requestof polling of sensor data), a data request from either the connector 150or the application server 424, or some other suitable event.

The application servers 424 can host big data analytics applicationscapable of using historical sensor data (e.g., measured and stored powerquality data and load management data and other sensor readings) toperform predictive analytics. Such predictive analytics can be used torecognize patterns in the historical data that are associated withfaults and then prognosticate or predict future, potential faults basedon current sensor data. In some implementations, raw sensor data ispacketized for transmission between the sensors, the connector 150, andthe application server 424. Big data analytics performed by theapplication servers 424 can use inductive statistics and concepts fromnonlinear system identification to infer rules or laws (e.g.,regressions, nonlinear relationships, and causal effects) from largesets of sensor data with low information density to perform predictionsof outcomes for network and electrical components in the systemarchitecture 500. For example, the application servers 424 can hostapplications that predict future malfunctions and faults for networkcomponents (e.g., BPL modems) and electrical components (e.g.,electrical conductors, BPL link connections). The application servers424 can also present, on a display device (not shown, but see displaydevice 914 in FIG. 9), functional health statuses and predicted outcomesfor network and electrical components in a GUI.

The system architecture 500 also includes a ground-based network 102. Insome implementations, the ground-based network 102 can be embodied as anIntranet providing Ethernet networking to communicatively couple theapplication servers 424 to the ground power system 130 (e.g., groundpower unit). As shown in FIG. 5, the ground power system 130 includes anoff-board BPL modem 414 and a coupler 416 (e.g., an inductive orcapacitive coupler). The off-board BPL modem 414 (e.g., a ground sideBPL modem or Power Line Communications (PLC) modem) functions as ahead-end master unit and provides interconnectivity to the ground-basednetwork 102.

The off-board BPL modem 414 can be coupled to a coupler 416. The coupler416 can be embodied as an inductive or capacitive coupler which isoperable to couple the off-board BPL modem 414 to one phase of the ACpower lines (e.g., stinger AC lines) that are included in the multi-usepower interface 110 (e.g., stinger cable). According to someimplementations, coupling to two AC phases is preferred as the BPLsignal is then further induced into the third phase since all threephases are typically included in a multi-use power interface 110. TheseAC power lines are labelled as AC Line Phase 1, AC Line Phase 2, and ACLine Phase 4 in FIG. 5. In some implementations, the ground power system130 is located at an aircraft stall for an aircraft vehicle 120 andprovides three phase 120 v AC 500 Hz [or 400 Hz] cycle electrical powerto the vehicle 120 via the AC power lines.

The system architecture 500 also includes the multi-use power interface110 that, when connected to the ground power system 130 and an aircraftvehicle 120 via the connector 150 and connector 140 of the vehicle 120,provides 4 phase 120 v AC 500 Hz cycle power to the aircraft. In someimplementations, the connector 150 is embodied as a stinger cable toaircraft plug that connects the multi-use power interface 110 to a PowerDistribution Unit (PDU) 513. In the example of FIG. 5, the PDU 513 is anaircraft Electronic and Equipment (EE or E&E) bay within the aircraftvehicle 120. However, in additional or alternative implementations, thePDU 513 can be located outside of the vehicle 120. As shown in FIG. 5,the PDU 513 includes an on-board BPL modem 411, which is another PLCmodem, and a coupler 515 (e.g., an inductive or capacitive coupler) thatis configured to couple the on-board BPL modem 411 to one phase of theAC power lines (e.g., stinger AC lines) that are included in themulti-use power interface 110 (e.g., stinger cable). The on-board BPLmodem 411 functions as an endpoint/slave or as a repeater and providesinterconnectivity to the ground-based network 102 (and the AC outlets614 of FIG. 6 when functioning as a repeater in repeater mode). Asshown, the vehicle 120 can include an Ethernet drop 518 from theon-board BPL modem 411 that provides Ethernet communications inside theaircraft vehicle 120.

As shown, the connector 150 can also include an endpoint BPL modem 514that is another PLC modem, and a coupler 516 (e.g., an inductive orcapacitive coupler) that is configured to couple the endpoint BPL modem514 to one phase of the AC power lines (e.g., stinger AC lines) that areincluded in the multi-use power interface 110 (e.g., stinger cable). Incertain implementations, the on-board BPL modem 411 can function as arepeater by simultaneously communicating with the off-board headend BPLmodem 414, the endpoint BPL modem 514 (which can also function as arepeater), and other on-board BPL modems 411 that may be present in thevehicle 120, and including an embedded BPL modem within a portabledis-connectable device which can be attached to connector 150 via theexternal wired communications interface 294 that is integrated into thehousing 250 of connector 150. Depending on vehicle on-board electricalconfigurations, on-board BPL modem 411 shown in FIGS. 4 and 5 may not berequired and the endpoint BPL modem 514 may be sufficient to providesupport of on-board BPL modem connectivity requirements instead of BPLmodem 411. The endpoint BPL modem 514 can function as an endpoint/slavedevice or a repeater and also provides sensing and testing dataconnectivity capability for the multi-use power interface 110. That is,the endpoint BPL modems 514 and 414 can serve as sensors that sense andtest BPL data links to determine whether they are functioning withinexpected performance ranges. The results of such sensing and testing canbe displayed on a user interface at the connector 150 (see, e.g., theuser interface 290 of FIG. 2) or remotely at a user interface of anapplication server 424. In some implementations, the use of the endpointmodem 514 in the system architecture 500 eliminates the need for theon-board BPL modem 411.

The system architecture 500 additionally includes a handheld BPL modem511. The handheld BPL modem 511 is a handheld PLC modem that includes anintegrated coupler that is used for detecting the AC line phase withinthe vehicle 120 that off-board BPL modem 414 is connected. In animplementation, the handheld BPL modem 511 can serve as a sensor thatdetects the status of the AC line phase for the AC power lines at thePDU 513.

In some implementations, the handheld BPL modem 511 or the endpoint BPLmodem 514 in repeater mode at the connector 150 can replace the need forthe on-board BPL modem 411 shown in FIGS. 4 and 5 and communicate withmodems 411 (and modems 616 shown in FIG. 6, described below). By usingarchitecture 500, network monitoring of BPL modem link connectivitystatus and data transmission performance can be performed whether themulti-use power interface 110 (e.g., stinger) is connected to thevehicle 120 (e.g., an aircraft) or not. Similarly, network management ofBPL modem configuration settings whether connected to aircraft or not.In various implementations, such network monitoring and management canbe performed locally at the connector 150, locally by a stand-alonedevice with a custom application, remotely at the application server424, or in a distributed manner, with some monitoring and/or managementtasks being performed by a computing device embedded in the connector150 (e.g., with a processor/CPU, a memory, and local storage) and somebeing performed by applications hosted by the application server 424.

In certain implementations, a wireless power charging interface can beadded to the connector 150 so that electronic packages can betemporarily mounted on the connector 150 (e.g., added to a stingerconnector). One example of the wireless power charging interface is aninductive or wireless charging interface. The electronic packages canalso be communicatively coupled to the connector 150 via wirelesscommunications connections and protocols, such as, for example, an NFCprotocol, a Bluetooth connection, a wired or wireless coupled BPL modemconnection, or a Wi-Fi connection. An example implementation includes aremovable electronic package comprising the endpoint BPL modem 514 andsensors where the removable package that can be taken out of theconnector 150 when needed. For example, the removable package can beelectrically and communicatively coupled to the connector 150 (e.g., viaa wireless power charging interface and the wireless communicationsinterface 292) in order to charge a battery of the removable package andto exchange data with the connector 150.

FIG. 6 is a diagram illustrating example system components for use inconnecting a multi-use power interface 110 to a vehicle 120, accordingto one or more implementations of the disclosure. In the example of FIG.6, the vehicle 120 includes AC outlets 614, which receive power from theAC power lines via the PDU 513. As shown, the vehicle 120 is connectedto the connector 150 via a connector 140 of the vehicle 120, and the ACoutlets 614 can be connected to the on-board BPL modem 411 via an ACpower strip 615 and the coupler 516 (e.g., inductive or capacitivecoupler in the vehicle 120). The on-board BPL modem 411 is alsocommunicatively coupled to the Ethernet drop 518, which providesEthernet communications inside the vehicle 120 (e.g., within anaircraft). As illustrated in FIG. 6, in additional or alternativeimplementations, the Ethernet drop 518 can be connected to the ACoutlets 614 via a home BPL modem 616. The home BPL modem 616 does notinclude or use an inductive coupler to couple the Ethernet drop 518 tothe AC outlets, which are in turn, connected to connector 150 via thePDU 513. In another alternative implementation shown in FIG. 6, the ACoutlets 614 can be connected via the AC power strip 615 with the homeBPL modem 616 plugged directly into AC power strip 615.

By using the system architecture 500 and system components shown inFIGS. 5 and 6, certain implementations carry out analytics of sensordata from the connector 150 (e.g., a smart stinger connector) at avehicle 120 (e.g., aircraft) interface. Sensors within the systemarchitecture 500, including, but not limited to TDRs, OTDRs, FDRs,accelerometers, moisture sensors, MFD detectors, ammeters, voltmeters,ohmmeters, Internet of Things (IoT) sensors, the handheld BPL modem 511,and the endpoint BPL modem 514, can monitor statuses of network andelectrical components, such as, for example, the AC power lines (e.g.,stinger AC lines) when the multi-use power interface 110 is connected ornot connected to the vehicle 120. Among other readings and measurements,the sensors can detect changes in standing waves at the connector 150.Also, the connector 150 can perform self-tests for frequency response,movement detection (i.e., based on accelerometer readings from anintegrated accelerometer within the connector 150), and tests fornetwork and electrical issues detected locally at the connector 150.

In this way, the architecture and components depicted in FIGS. 5 and 6enable real-time monitoring and management of BPL modem operations forBPL modems 411, 414, 511, and 514, as well as BPL data links modemlinks. The application server 424 can receive sensor data, store it ashistorical data, and perform analytics of the power line (e.g., stingerAC line) health history. The results of such analytics can be presentedin a display device of the application server 424, or locally at theconnector 150 with remote control of LEDs being used as statusindicators installed in the connector 150 (e.g., stinger connector) atthe vehicle 120 (e.g., aircraft) interface.

As described above with reference to FIG. 5, application software can behosted by the application server 424 and the application software canpresent a GUI for rendering real-time analysis of functional healthstatuses for data and power links in the multi-use power interface 110(e.g., stinger health) and BPL modem operations. For example, networkmonitoring performed by off-board BPL modem 414 can be reported assensor data to the application server 424 (or a stand-alone device) viaground-based network 102, and then saved at the application server 424(or the stand-alone device) for subsequent analysis and display. Thesensor data can be stored as historical data in a memory orcomputer-readable storage device of the application server 424 (or thatof a stand-alone device). The saved sensor data representing the networkmonitoring can also be used by the application server 424 to performdata analytics (e.g., predictive analytics) in order to identify trendsthat have led to previous electrical issues and network issues (e.g.,bandwidth issues or communications failures) in order to aid inpreventing future, predicted electrical and network issues. In someimplementations, the application server 424 can report data to theconnector 150. For example, the application server 424 can send, via theground-based network 102, historical data to the connector 150 and theconnector 150 can then compare the historical data to locally stored,presently detected data in order to provide feedback at the connector150 when potential issues are detected. In this example, the connector150 can illuminate an LED in the user interface 290 as a fault indicatorwhen the comparison of ambient temperature readings with historical datafrom the application server 424 indicates that the connector 150 may beoverheating.

The architecture and components of FIGS. 2-6 can provide an immediatestatus at the connector 150. For example, the user interface 290 caninclude multicolor LEDs and/or strobe lights that can be illuminated inpredefined patterns to show healthy electrical and data connections. Incertain implementations, a green LED can indicate a good, expectedvoltage reading, and a blinking green LED can indicate good networkconnectivity (e.g., data transfer rates within an expected range). Inadditional or alternative implementations, this immediate status canalso be provided at a user interface of server 424 and/or a userinterface of a mobile device such as a smartphone or tablet devicecarried by a mechanic or member of a ground crew. In the latter example,the mobile device can be communicatively coupled to the applicationserver 424 via the ground-based network 102 or wirelessly (e.g., via aBluetooth connection to the connector 150). Such user interfaces canshow predictive elements based on health check data read at theconnector 150. Such predictive elements can include one or more of phasedrift or current spikes. When such predictive elements are detectedbefore the connector 150 is connected to the vehicle 120, a user (e.g.,a mechanic or ground crewmember at an airport) will readily be able todetermine that the issue is not with the vehicle plane, but is isolatedto the connector 150.

Certain implementations of the architecture and components of FIGS. 2-6can also flag conditions that could lead to failure of electricalcomponents of the connector 150. For example, the connector can detectand report on conditions indicative of corrosion, or broken pins (see,e.g., pins 210 a, 210 b, 210 c, 220, 230 a and 230 b of FIG. 2) on theconnector 150. Such conditions can be detected by an accelerometer thatflags physical trauma or shocks inflicted on the connector 150, athermometer that flags extreme temperature fluctuations, or a multimeterthat detects out of range current or voltage fluctuations (e.g., largevoltage surges or voltage drops/reductions). Sensors can also detectnoise on an electrical line (e.g., an AC power line). Such detectednoise can indicate potential failure of the connector 150 and can beused to isolate problems on the connector 150 side (e.g., outside thevehicle 120). By isolating problems in this way, implementations reducefaulty diagnoses of vehicles 120 and reduce wasted troubleshooting timefor a network-based vehicle 120 (e.g. a network-based airplane).

Some implementations of the architecture and components of FIGS. 2-6also enable data collection to support big data analytics, healthprognostication, monitoring, and reporting for the network andelectrical components shown in these Figures. For instance, big dataanalytics can be performed by the application server 424 to enablepredictive maintenance for the components shown in FIGS. 2-6. That is,big data analytics can be used to predict, based on analyzing trends inhistorical data for similar components (e.g., electrical andcommunications components having similar characteristics and operationalparameters), when component maintenance should be carried out in orderto prevent component faults or failures. By performing such big dataanalytics, the system architecture 500 of FIG. 5 supports componenthealth. The collected data can be stored in the sever 424 and caninclude historical health data for the vehicle 120, the connector 150,the multi-use power interface 110, and BPL modems 411, 414, 511 and 514.The architecture and components of FIGS. 4 and 5 also allow the systemto be characterized, which enables cross checking an impedancecharacteristic of the gate power source at the ground power system 130as well as characterizing an electrical load characteristic of thevehicle 120 (e.g., airplane electrical load characteristic). Suchcharacterizations can be at least partially preformed prior to theconnector 150 being mated to or connected to the vehicle 120.

Certain implementations can compare sensor readings to thresholds thatare fixed/predetermined (e.g., upper/lower currents, voltages, MFD, ordata transfer rates in order to detect or predict faults. Additional oralternative implementations can provide feedback in real time to triggeralerts at the connector 150. For example, a combination of informationbeing processed back at the application server 424 can indicate that theconnector is heading towards a threshold exceedance and provide feedbackto this effect at the user interface 290 of the connector 150 so thatusers (e.g., ground crew members or maintenance personnel) will benotified. In one non-limiting example, the application server 424 cananalyze temperature, voltage, and current readings taken over the courseof three shifts in a day to create a temperature, voltage, and currentprofiles, and can then illuminate an LED in the user interface 290 sothat maintenance crew members working the third shift are notified thatthe connector 150 is headed for an overheat condition (or in an overheatcondition). This notification is based on analyzing the temperature andcurrent profiles. The temperature and current profiles can be analyzedtogether as current carrying capacities of electrical conductors (e.g.,wires and cables) decrease as their temperatures increase. In a similarmanner, voltage profiles can be analyzed to determine that a potentialvoltage issue (e.g., a voltage surge or reduction that is outside of athreshold value) will arise at the connector 150. The application server424 can provide additional intelligence that local instruments at theconnector 150 would not have in real time, but that the applicationserver 424 can identify based on analytical trending data. For example,the application server 424 would be able to gather this additionalintelligence and then without requiring the connector to retrieve datafrom a data store or database, the application server 424 can instructthe user interface 290 to illuminate a discreet LED to alert maintenancepersonnel. In additional or alternative implementations, the alert canbe more sophisticated than illuminating an LED. For instance, anindication can be displayed in a GUI (included in the user interface290, in a GUI of the application server 424), communicated via email(e.g., SMTP), instant message, or a short message service (SMS) textmessage sent to ground crew members, mechanics, or maintenancepersonnel, or indicated in the GUI of a mobile device carried by orassociated with such personnel. In this way, the system architecture 400leverages additional knowledge gathered by the application server 424and displays it in real time.

FIG. 7 illustrates a flowchart of a method 700 for monitoring andanalyzing data collected at a multi-use power interface in order todetect and predict health statuses of components of electrical andnetwork systems, according to an implementation. The method 700 can useprocessing logic, which can include software, hardware, or a combinationthereof. The monitoring can be via SNMP, TR-069, installed health agentor other. For example, the method 700 can be performed by a systemincluding one or more components described above with reference to thesystem 400 of FIG. 4 (e.g., application server 424 and connector 150).

As shown, at 702, the method 700 includes measuring and/or receiving (atleast a portion of) power quality data and load management data fromsensors that are operable to collect power quality data and loadmanagement data for BPL data links and a multi-use power interface. Asshown in FIG. 7, the multi-use power interface is operable to beelectrically and communicatively coupled to a vehicle via the BPL datalinks. According to implementations, the multi-use power interface canbe embodied as multi-use power interface 110 shown in FIGS. 1-6 and thevehicle can be embodied as the vehicle 120 shown in FIGS. 1 and 4-6.

At 704, the method 700 also includes determining, based on the powerquality data and load management data, functional health statuses of themulti-use power interface and the BPL data links. As shown in FIG. 7,704 can include comparing the data received at 702 to functional healththresholds. As shown, 704 can also include predicting future statusesbased on the data (i.e., prognosticating potential future faults ormalfunctions based on using analytics to identify patterns in stored,historical data).

At 706, the method 700 further includes transmitting the functionalhealth statuses, the power quality data, and the load management data toa data store. As shown in the example of FIG. 7, 706 can include sendingthe functional health statuses, the power quality data, and the loadmanagement data to a database. In some implementations, the data storeor database can be local to the connector 150 shown in FIGS. 1, 2 and4-6 and the detachable adapter 350 shown in FIG. 3. In additional oralternative implementations, the data store or database can be hosted bya server (e.g., server 424) that is remote from the connector 150 andthe detachable adapter 350 of FIG. 3. In some implementations, the datastore is remote to the multi-use power interface 110, the connector 150and the detachable adapter 350, and monitored data is transmitted alongwith the functional health statuses, the power quality data, and theload management data to the data store via a BPL modem over one or moreBPL data links of the multi-use power interface 110 using BPLcommunications.

At 708, the method 700 additionally includes indicating, in a userinterface, the functional health statuses. As shown in FIG. 7, 708 caninclude providing the functional health statuses and/or predicted futurestatuses to a display device. For example, 708 can include indicating orrepresenting the functional health statuses on a display device used topresent the user interface 290 at the connector 150 or at the detachableadapter 350 as shown in FIGS. 2 and 3. In alternative or additionalimplementations, 708 can include displaying the functional healthstatuses in a GUI from the application information within theapplication server 424. In alternative or additional implementations,708 can include reporting faults to a network monitoring server. Incertain implementations, 708 can also include indicating results ofanalytics performed on stored data. For example, 708 can includepresenting results of big data analytics performed as a part of 704.Such results can include predictions based on patterns in stored,historical data and known past events (e.g., component failures andfaults in electrical connections), as well as conditions that could leadto future failure and fault events (e.g., current or voltagefluctuations, overheating, moisture, physical trauma or shocks inflictedon the connector 150). That is, the results of analysis performed at 704can be presented at 708 as health prognostications for components of themonitored electrical and network systems.

FIG. 8 illustrates a flowchart of a method 800 for performing predictiveanalytics with collected sensor data and BPL data, according to one ormore implementations of the disclosure. The method 800 can useprocessing logic, which can include software, hardware, or a combinationthereof. For example, the method 800 can be performed by a systemincluding one or more components described above with reference to thesystem 400 of FIG. 4 (e.g., server 424 and connector 150).

The method 800 uses predictive analytics and artificial intelligence tocomplete machine learning tasks such as regression, classification,collaborative filtering, ranking, and event prediction (e.g., equipmentfailure prediction). Some implementations of the method 800 leveragepredictive analytics techniques to provide a prediction algorithm thatruns in linear time and predicts equipment failure. Machine learning canbe used to predict data that can exist in the real world (e.g., at anairport). Machine learning typically relies on providing positive truesamples (e.g., past events such as equipment failures) and negativefalse samples, and teaching a machine (e.g., an application server 424or other computing device) to distinguish between the positive andnegative samples. Positive real-world data can be obtained by completingoperations 802-806, which are described below. For example, in a machinelearning algorithm that uses an individual component's history of faultsand failures to predict a pending failure, positive samples can beobtained from the parameters measured and captured in operations 802 and806.

As shown, at 802, the method 800 includes measuring and/or receiving,and storing (at least a portion of) data representing physicalparameters related to electrical power transmission and data transfer.The parameters can be measured by sensors and can correspond to BPL datalinks and a multi-use power interface. The multi-use power interface canbe configured to be electrically and communicatively coupled to avehicle via the BPL data links. According to implementations, themulti-use power interface can be embodied as multi-use power interface110 shown in FIGS. 1-6 and the vehicle can be embodied as the vehicle120 shown in FIGS. 1 and 4-6. In some implementations, 802 includesstoring the measured and/or received data representing physicalparameters in a data store or database. In certain implementations, thedata store or database can be local to the connector 150 shown in FIGS.1, 2 and 4-6 and the detachable adapter 350 shown in FIG. 3. Inadditional or alternative implementations, the data store or databasecan be hosted by a server (e.g., application server 424) that is remotefrom the connector 150 and the detachable adapter 350 of FIG. 3. In someimplementations, the data store is remote to the multi-use powerinterface 110, the connector 150 and the detachable adapter 350, and themeasured and/or received parameters are transmitted to the data storevia a BPL modem over one or more BPL data links of the multi-use powerinterface 110 using BPL communications.

As shown in the example of FIG. 8, the parameters related to electricalpower transmission measured and stored at 802 can include one or more ofvoltage, current, unit temperature (e.g., internal temperature of anelectrical or network component), ambient temperature (e.g., airtemperature where an electrical or network component is located such asan airport jetway), and accelerometer readings. As further shown in FIG.8, the parameters related to data transfer that are measured, received,and stored at 802 can include one or more of the following: data rate,ping retries, packet loss (e.g., a percentage of packets lost withrespect to packets sent to a network component), latency, and jitter.

According to some implementations, the parameters related to electricalpower transmission that are measured and stored at 802 form anelectrical domain, and the parameters related to data transfer that aremeasured and stored at 802 form a data domain. In such embodiments, theelectrical domain and the data transfer domain can be used as analyticalcross-checks. For example, the two sets of data (i.e., in the electricaldomain and data transfer domain) serve to amplify the use of big dataanalytics in the method 800, thus increasing the overall amount ofstatistically significant information, and enabling identification of awider range of valuable correlations and predictive trendinginformation.

At 804, the method 800 also includes recording identifiers of aconnector for a multi-use power interface (e.g., stinger connector).According to implementations, the connector for the multi-use powerinterface can be embodied as the connector 150 for the multi-use powerinterface 110 shown in FIGS. 1, 2, and 4-6. In additional or alternativeimplementations, the connector can be embodied as the detachable adapter350 and the standard connector 355 shown in FIG. 3. In the example ofFIG. 8, the identifiers of the connector include a part number (P/N) andserial number (S/N) of the multi-use power interface. As shown in FIG.8, 804 also includes recording a time (e.g., a timestamp), and a gatelocation. In the example of FIG. 8, the gate location can be recorded asgate identifier for an airport (e.g., gate N-8 at Sea-TAC airport) or asGlobal Positioning System (GPS) coordinates (e.g., latitude andlongitude). As further shown in FIG. 8, 804 can include recording a gatebox part number (P/N) and serial number (S/N), and a vehicle identifier.In the example of FIG. 8, the vehicle identifier can be an aircraft tailID or a vehicle identification number (VIN).

At 806, the method 800 also includes detecting a change of a connectorfor a multi-use power interface (e.g., a stinger connector). As shown inFIG. 8, the change record can be facilitated several ways byimplementing one or more of the following techniques: the change can bemanually entered, the change can be recorded by an RFID tag reader(e.g., reading RFID tag on a connector 150), the change can be recordedby an optical reader (e.g., reading an optical bar code on the connector150), or the change can be recorded as an impedance characterization. Inthe example of FIG. 8, such impedance characterizations can include oneor more of an open circuit voltage, short circuit current, harmonics,and other characterizations of electrical impedance. In someimplementations, such impedance characterizations trigger a data logcapture of parameters leading up to the detected change (e.g., equipmentchange, equipment fault, or equipment failure detected at theconnector). The captured parameters can include one or more of a gatebox type, an ambient temperature, an outside temperature, an averagecurrent, and a utilization rate.

According to some implementations, 806 includes detecting a change in amemory of the connector 150, a change in a network characteristic ornetwork component, a change in an airport gate box, a change in a GPSlocation or coordinate, or a location change detected by a globalnavigation satellite system (GNSS). In additional or alternativeimplementations, 806 includes detecting a change with sensors such as,for example, an accelerometer (e.g., an accelerometer integrated intothe connector 150), a voltmeter, a current meter, a vector analyzer, anda spectrum analyzer. In accordance with certain implementations, 806includes one or more of detecting a change in a data rate for a datacommunication link or data communication path, detecting a change inamplitude, detecting a frequency change, and detecting a phase change.

At 808, the method 800 further includes identifying trends byparameters. In the example of FIG. 8, the parameters can includemeasurements indicating one or more of a voltage, a temperature, acurrent, harmonics, shock, utilization (e.g., a percentage utilizationfor an electrical or network component), vehicle type (e.g., aircrafttype), generator type, equipment (e.g., an equipment identifier for anelectrical or network component), a measure of moisture, a measure ofprecipitation, and time (e.g., a timestamp). In some implementations,808 can include comparing the parameters to historical data thatincludes previously measured and stored parameters that were obtained asa result of previous iterations performing operations 802-806. Inadditional or alternative implementations, the parameters used at 808for identifying trends are not limited to those shown in FIG. 8. Forinstance, the parameters used at 808 can include historical data such aspreviously measured parameters obtained by prior iterations of operation802.

At 810, the method 800 additionally includes identifying parametersexperiencing change in advance of a failure of a network or electricalcomponent. In some implementations, 810 can include using predictiveanalytics algorithms to examine historical parameter readings (e.g.,historical data measured and captured in past iterations of 802 and 804)from a data store or database and identifying which parameters changed,and what the patterns of change were prior to a failure of a network orelectrical component. For example, the parameters captured at 806 can beused at 810 to identify trending preconditions leading to equipmentfailure. In this way, the method 800 enables monitoring thresholds ofpre-failure. In some implementations, the data store or database can belocal to the connector 150 shown in FIGS. 1, 2 and 4-6 and thedetachable adapter 350 shown in FIG. 3. In additional or alternativeimplementations, the data store or database can be hosted by a server(e.g., application server 424) that is remote from the connector 150 andthe detachable adapter 350 of FIG. 3. In some implementations, the datastore is remote to the connector 150 and the detachable adapter 350, andthe measured parameters are transmitted to the data store via a BPLmodem over one or more BPL data links of the multi-use power interface110 using BPL communications.

At 812, the method 800 also includes interrogating the memory of theconnector (e.g., a local memory of the connector 150) for parameter dataand sending alerts to stakeholders of pending failures. In certainembodiments, the stakeholders can include, for example, airlines,airports, original equipment manufacturers (OEMs), and power generationcompanies (e.g., electric utilities).

By executing and repeating operations 802-812, a first feedback loopcollects data and the method 800 looks for similar conditions toprevious network and electrical equipment failures. By using theparameters from 802, 806, and 806 to identify similar conditions (e.g.,parameters) that correlated to previous failures, 808-812 can beexecuted to predict or prognosticate pending failures.

At 814, the method 800 further includes modifying the frequency ofparameter collection. In the example of FIG. 8, modifying frequencies ofparameter collection can be performed by changing a sample rate for aparameter. For instance, as shown in FIG. 8, 814 can include increasingsampling rates for parameters such as temperature readings in responseto determining that such parameters highly correlate to equipmentfailure. That is, if it is determined that there is a high correlationbetween temperature fluctuations (e.g., temperature spikes, extremes, orhigh temperatures) and equipment failure, 814 can include increasing asample rate for temperature readings in order to improve failure rateprognostication. As also shown in FIG. 8, 814 can include decreasing oreliminating sample rates for other parameters, such as moistureinformation, responsive to determining that such parameter readings havelittle or no correlation to system performance or equipment failure rateprognostication.

As shown in FIG. 8, at 814, the frequency of parameter collection ismodified as an adaptive, dynamic element of a predictive analyticsalgorithm. The respective frequencies for collection of parameters canbe tunable values that can be manually modified. In additional oralternative implementations, the parameter collection frequencies can beautomatically adjusted at 814 based on using artificial intelligence andcompleting machine learning tasks such as regression, classification,collaborative filtering, ranking, and event prediction (e.g., equipmentfailure prediction) and correlating parameters to events. In yet otheradditional or alternative implementations, the parameter collectionfrequencies can be adjusted at 814 in a hybrid manner. That is, thecollection frequencies for parameters can be adjusted using acombination of manual modification and automatic modification.

After the parameter collection frequencies are adjusted at 814, controlis passed back to 802 so that the parameters can be collected accordingto the adjusted parameter collection frequencies.

By repeating operations 802-814 a second feedback loop can modify thetype of data collected and processed improving the predictive analyticsalgorithm. By using the method 800, a mean time between failure (MTBF)can be compiled for various network and electrical components, where theMTBF is the predicted elapsed time between inherent failures of anetwork or electrical component (e.g., in the system 400 of FIG. 4during normal operation of the system 400. In certain implementations,the MTBF compiled by the method 800 is calculated as the arithmetic mean(average) time between failures of a network or electrical component ofthe system 400 of FIG. 4 or the system architecture 500 of FIG. 5. Inaccordance with certain implementations, the method 800 compiles MTBFvalues for repairable or replaceable network and electrical components.The method 800 can use its own data and add it to historical data, andin some cases, trending data can be exported to or imported into othersystems in order to have more data for the analytics data to beimproved. The method 800 also provides intelligence on ground powergeneration equipment (e.g., ground power system 130) and airplane loadanalysis. The method 800 looks for correlations between parameters andevents for various electrical and network components of the system shownin FIG. 4 (e.g., airplane vehicle 120, multi-use power interface 110,and the ground power system 130).

Synthesized data resulting from the method 800 can be transmitted orrouted to several stakeholders, such as, for example, airlines,airports, original equipment manufacturers (OEMs), and power generationcompanies (e.g., electric utilities).

As show in FIG. 8 and noted above, the operations of the method 800described above can be iteratively executed. That is, operations 802-814can be repeated so that the method 800 includes multiple phases forusing sensor data and BPL data for predictive analytics to predict whenelectrical and network components may have events (e.g., experiencefaults or failures or otherwise require maintenance). These phases caninclude a first phase where initially, predictive analytics algorithmsare used to look for trends. In particular, these algorithms identifytrends with a focus on health of a multi-use power interface (e.g.,stinger health). In a second phase, the algorithms can be improved tofocus on the most valuable parameters (see, e.g., the parametersmeasured at 802, described above) at the optimal sample period. In athird phase, the algorithms look at trends in the health of a vehicle(e.g., airplane health). In a fourth phase, the algorithms look attrends in health of ground power generation equipment (e.g., health of aground power system 130 or a ground power unit).

FIG. 9 is a block diagram illustrating an example of a computing system900 that can be used in conjunction with one or more implementations ofthe disclosure. In certain implementations, the computing system 900 canbe used to implement the application server 424 in FIGS. 4 and 5.According to some implementations, the computing system 900 can be usedto implement the computing device 422 of the ground power system 130shown in FIG. 4. In accordance with certain implementations, thecomputing system 900 can also be used to implement the on-board server426 of the vehicle 120 shown in FIG. 4. In the example of FIG. 9, thecomputing system 900 includes a communications framework 902, whichprovides communications between processor unit 904, memory 906,persistent storage 908, communications unit 910, input/output (I/O) unit912, and display device 914. In some implementations, the display devicecan be used to implement the user interface 290 in FIGS. 2 and 3. Forexample, an embedded touchscreen display device integrated into housing250 of the connector shown in FIG. 2 can be used to present the userinterface 290. Similarly, an embedded touchscreen display deviceintegrated into of the detachable adapter 350 shown in FIG. 3 can beused to present the user interface 290. With continued reference to theexample of FIG. 9, the communications framework 902 can take the form ofa bus system.

The processor unit 904 serves to execute instructions for software thatcan be loaded into the memory 906. The processor unit 904 can be anumber of processors, a multi-processor core, or some other type ofprocessor, depending on the particular implementation.

The memory 906 and the persistent storage 908 are examples of storagedevices 916. A storage device is any piece of hardware that is capableof storing information, such as, for example, without limitation, atleast one of data, program code in functional form, or other suitableinformation either on a temporary basis, a permanent basis, or both on atemporary basis and a permanent basis. The storage devices 916 can alsobe referred to as computer-readable storage devices in theseillustrative examples. The memory 906, in these examples, can be, forexample, a random-access memory or any other suitable volatile ornon-volatile storage device. The persistent storage 908 can take variousforms, depending on the particular implementation.

For example, the persistent storage 908 can contain one or morecomponents or devices. For instance, the persistent storage 908 can be ahard drive, a solid state hard drive, a flash memory, a rewritableoptical disk, a rewritable magnetic tape, or some combination of theabove. The media used by persistent storage 908 also can be removable.For example, a removable hard drive can be used to implement thepersistent storage 908. The storage devices 916 can comprisenon-transitory computer-readable media storing instructions, that whenexecuted by the processor unit 904, cause the computing system 900 toperform operations.

The communications unit 910, in example implementations, provides forcommunications with other data processing systems or devices. In theseillustrative examples, the communications unit 910 is embodied as anetwork interface card.

The input/output unit 912 allows for input and output of data with otherdevices that can be connected to computing system 900. For example, theinput/output unit 912 can provide a connection for user input through atleast one of a keyboard, a pointing device (e.g., a stylus), a mouse, atouchscreen display device (e.g., an embedded touchscreen display usedto implement the user interface 290 of FIGS. 2 and 3), a trackpad, atouch pad, or some other suitable input device. Further, input/outputunit 912 can send output to a printer. Display device 914 provides amechanism to display information to a user, such as, for example a userof the connector 150 of FIG. 2, a user of the detachable adapter 350 ofFIG. 3, a user of the application server 424 of FIGS. 4 and 5, a user ofthe computing device 422 of FIG. 2, or a user of the on-board server 426of FIG. 4.

Instructions for at least one of the operating system, applications, orprograms can be located in the storage devices 916, which are incommunication with the processor unit 904 through the communicationsframework 902. The processes and methods of the differentimplementations can be performed by the processor unit 904 usingcomputer-implemented instructions, which can be located in a memory,such as the memory 906. For example, the operations of the methods 700and 800 described above with reference to FIGS. 7 and 8 can be performedby the processor unit 904 using computer-implemented instructions.

These instructions are referred to as program code, computer usableprogram code, or computer-readable program code that can be read andexecuted by a processor in the processor unit 904. The program code inthe different implementations can be embodied on different physical orcomputer-readable storage media, such as the memory 906 or persistentstorage 908.

Program code 918 is located in a functional form on computer-readablemedia 920 that is selectively removable and can be loaded onto ortransferred to the computing system 900 for execution by the processorunit 904. The program code 918 and computer-readable media 920 formcomputer program product 922 in these illustrative examples. In theexample, computer-readable media 920 is computer-readable storage media924. In these illustrative examples, computer-readable storage media 924is a physical or tangible storage device used to store program code 918rather than a medium that propagates or transmits program code 918.

Alternatively, the program code 918 can be transferred to the computingsystem 900 using a computer-readable signal media. The computer-readablesignal media can be, for example, a propagated data signal containingthe program code 918. For example, the computer-readable signal mediacan be at least one of an electromagnetic signal, an optical signal, orany other suitable type of signal. These signals can be transmitted overat least one of communications links, such as wireless communicationslinks, optical fiber cable, coaxial cable, a wire, or any other suitabletype of communications link such as, for example, BPL data linksincluded in the multi-use power interface 110 of FIGS. 1-6.

The different components illustrated for the computing system 900 arenot meant to provide architectural limitations to the manner in whichdifferent implementations can be implemented. The different illustrativeimplementations can be implemented in a data processing system includingcomponents in addition to or in place of those illustrated for thecomputing system 900. Other components shown in FIG. 9 can be variedfrom the illustrative examples shown. The different implementations canbe implemented using any hardware device or system capable of runningthe program code 918.

While the present teachings have been illustrated with respect to one ormore implementations, alterations and/or modifications can be made tothe illustrated examples without departing from the spirit and scope ofthe appended claims. For example, it will be appreciated that while theprocess is described as a series of acts or events, the presentteachings are not limited by the ordering of such acts or events. Someacts may occur in different orders and/or concurrently with other actsor events apart from those described herein. For example, operations andphases of the methods have been described as first, second, third, etc.As used herein, these terms refer only to relative order with respect toeach other, e.g., first occurs before second. Also, not all processstages may be required to implement a methodology in accordance with oneor more aspects or implementations of the present teachings. It will beappreciated that structural components and/or processing stages can beadded or existing structural components and/or processing stages can beremoved or modified. Further, one or more of the acts depicted hereinmay be carried out in one or more separate acts and/or phases.Furthermore, to the extent that the terms “including,” “includes,”“having,” “has,” “with,” or variants thereof are used in either thedetailed description and the claims, such terms are intended to beinclusive in a manner similar to the term “comprising.” The term “atleast one of” is used to mean one or more of the listed items can beselected. As used herein, the term “one or more of” with respect to alisting of items such as, for example, A and B, means A alone, B alone,or A and B. The term “at least one of” is used to mean one or more ofthe listed items can be selected. Further, in the discussion and claimsherein, the term “on” used with respect to two materials, one “on” theother, means at least some contact between the materials, while “over”means the materials are in proximity, but possibly with one or moreadditional intervening materials such that contact is possible but notrequired. Neither “on” nor “over” implies any directionality as usedherein. The term “conformal” describes a coating material in whichangles of the underlying material are preserved by the conformalmaterial. The term “about” indicates that the value listed may besomewhat altered, as long as the alteration does not result innonconformance of the process or structure to the illustratedimplementation. Finally, “exemplary” indicates the description is usedas an example, rather than implying that it is an ideal. Otherimplementations of the present teachings will be apparent to thoseskilled in the art from consideration of the specification and practiceof the disclosure herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the present teachings being indicated by the following claims.

It will be appreciated that variants of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be combined intomany other different systems or applications. Various presentlyunforeseen or unanticipated alternatives, modifications, variations, orimprovements therein can be subsequently made by those skilled in theart which are also intended to be encompasses by the following claims.

What is claimed is:
 1. A system for analyzing data characterizingelectrical and network components, the system comprising: a plurality ofsensors configured to measure physical parameters related to electricalpower transmission and physical parameters related to data transfer; anda server comprising a processor, and a memory storing instructionsthereon, that when executed by the processor, cause the server toperform operations including: receiving identification information,location information, and a timestamp associated with a connector of amulti-use power interface; storing, in the memory, measurements of thephysical parameters, the identification information, the locationinformation, and the timestamp; detecting a change of the connector ofthe multi-use power interface; identifying trends in parameters bycomparing the stored measurements of the physical parameters, the storedidentification information, and the stored location information tohistorical data; predicting, based on correlating the identified trendsto the detected change, a pending failure of one or more of a networkcomponent and an electrical component; and transmitting an indication ofthe pending failure.
 2. The system of claim 1, wherein the physicalparameters related to electrical power transmission comprise one or moreof a voltage, a current, a unit temperature, an ambient temperature, andan accelerometer reading.
 3. The system of claim 2, wherein the unittemperature is an internal temperature of an electrical component, andwherein the ambient temperature is an air temperature where theelectrical component is located.
 4. The system of claim 1, wherein thephysical parameters related to data transfer includes at least one of adata rate, a number of ping retries, a packet loss measurement, alatency, and a jitter measurement.
 5. The system of claim 4, wherein thepacket loss measurement is a percentage of packets lost with respect topackets sent to a network component.
 6. The system of claim 1, whereinthe operations further include: modifying a frequency for measuring ofone or more of the physical parameters in response to determining acorrelation of the one or more of the physical parameters to predictinga pending failure of one or more of a network component and anelectrical component; and repeating the receiving, the storing, thedetecting, the identifying, the predicting, and the transmittingaccording to the modified frequency.
 7. The system of claim 1, whereinthe identification information comprises one or more of a serial numberof the connector of the multi-use power interface and a part number ofthe connector of the multi-use power interface, and wherein the locationinformation comprises one or more of Global Positioning System (GPS)coordinates of the connector of the multi-use power interface and a gatelocation of the connector of the multi-use power interface.
 8. Thesystem of claim 1, wherein detecting a change of the connector of themulti-use power interface comprises one or more of detecting a manuallyentered change, detecting a change recorded by a radio-frequencyidentification (RFID) tag reader, detecting a change recorded by anoptical reader, and detecting a change in an impedance characterization.9. The system of claim 8, wherein detecting the change in the impedancecharacterization comprises one or more of detecting an open circuitvoltage, detecting a short circuit current, and detecting a change inharmonics.
 10. The system of claim 1, wherein the historical dataincludes previously measured parameters indicating one or more of avoltage, a temperature, a current, harmonics, a shock, utilization, avehicle type, a generator type, an equipment identifier, a moisturemeasurement, and a precipitation measurement.
 11. The system of claim 1,wherein identifying trends in parameters comprises identifyingparameters experiencing change in advance of one or more of a previousfailure of a network component indicated in the historical data and aprevious failure of an electrical component indicated in the historicaldata.
 12. The system of claim 1, wherein transmitting the indicationcomprises transmitting the indication to one or more of an airline, anairport, an original equipment manufacturer (OEM), and a powergeneration company.
 13. The system of claim 1, wherein the plurality ofsensors includes one or more of a time domain reflectometer (TDR) and afrequency domain reflectometer (FDR) configured to measure the physicalparameters related to electrical power transmission by characterizingelectrical conductors in a plurality of Broadband over Power Line (BPL)data links.
 14. The system of claim 1, wherein the storing comprisesstoring the measurements of the physical parameters, the identificationinformation, the location information, and the timestamp in a data storeof the server.
 15. The system of claim 1, wherein the multi-use powerinterface further comprises: a plurality of pins for electrically andcommunicatively coupling the multi-use power interface to a vehicle viaa plurality of Broadband over Power Line (BPL) data links; electricalconductive materials for a three-phase alternating current (AC) powerinterface with the vehicle; and one or more Gigabit fiber optic datalinks.
 16. The system of claim 15, wherein the plurality of sensorsinclude at least one optical time domain reflectometer (OTDR) configuredto collect load management data by characterizing the one or moreGigabit fiber optic data links.
 17. A computer implemented method foranalyzing data characterizing electrical and network components, themethod comprising: obtaining, from a plurality of sensors, measurementsof physical parameters related to electrical power transmission andphysical parameters related to data transfer; receiving identificationinformation, location information, and a timestamp associated with aconnector of a multi-use power interface; storing, in a memory,measurements of the physical parameters, the identification information,the location information, and the timestamp; detecting a change of theconnector of the multi-use power interface; identifying trends inparameters by comparing the stored measurements of the physicalparameters, the stored identification information, and the storedlocation information to historical data; predicting, based oncorrelating the identified trends to the detected change, a pendingfailure of one or more of a network component and an electricalcomponent; and transmitting an indication of the pending failure. 18.The method of claim 17, further comprising: modifying, by the computingdevice, a frequency for measuring of one or more of the physicalparameters in response to determining a correlation of the one or moreof the physical parameters to predicting a pending failure of one ormore of a network component and an electrical component; and repeatingthe receiving, the storing, the detecting, the identifying, thepredicting, and the transmitting according to the modified frequency.19. The method of claim 17, wherein the physical parameters related toelectrical power transmission comprise one or more of a voltage, acurrent, a unit temperature, an ambient temperature, and anaccelerometer reading, wherein the unit temperature is an internaltemperature of an electrical component, and wherein the ambienttemperature is an air temperature where the electrical component islocated, and wherein the physical parameters related to data transferincludes at least one of a data rate, a number of ping retries, a packetloss measurement, a latency, and a jitter measurement, and wherein thepacket loss measurement is a percentage of packets lost with respect topackets sent to a network component.
 20. The method of claim 17, whereinidentifying trends in parameters comprises identifying parametersexperiencing change in advance of one or more of a previous failure of anetwork component indicated in the historical data and a previousfailure of an electrical component indicated in the historical data. 21.The method of claim 17, wherein the plurality of sensors include one ormore of a time domain reflectometer (TDR) and a frequency domainreflectometer (FDR) configured to measure the physical parametersrelated to electrical power transmission by characterizing electricalconductors in a plurality of Broadband over Power Line (BPL) data links.